Skip to content

OCPBUGS-101991: CVE-2026-33814 openshift4/ose-monitoring-plugin-rhel9: Go HTTP/2: Denial of Service via malformed SETTINGS_MAX_FRAME_SIZE frame [openshift-4.22] - #1202

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.22from
tonyxrmdavidson:OCPBUGS-101991-CVE-2026-33814-4-22
Sep 16, 2026
Merged

openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.22from
tonyxrmdavidson:OCPBUGS-101991-CVE-2026-33814-4-22

Conversation

@tonyxrmdavidson

Copy link
Copy Markdown

Remediates CVE-2026-33814, a denial-of-service vulnerability in Go's HTTP/2 implementation (golang.org/x/net) where a malformed SETTINGS_MAX_FRAME_SIZE frame can be used to crash or hang a server.

Changes

  • Added a replace directive in go.mod pointing golang.org/x/net to the patched fork github.com/openshift-sustaining/net@v0.50.0-sec.4.
  • Bumped golang.org/x/net from v0.34.0 → v0.49.0 (via the replace) along with transitively affected golang.org/x/sys, golang.org/x/term, and golang.org/x/text to satisfy go mod tidy.
  • Updated go.sum accordingly.

Testing

  • make build-backend — builds successfully with go 1.24.0.
  • make test-backend — all tests in ./pkg/... pass.

…rhel9: Go HTTP/2: Denial of Service via malformed SETTINGS_MAX_FRAME_SIZE frame [openshift-4.22]
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 31, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@tonyxrmdavidson: This pull request references Jira Issue OCPBUGS-101991, which is invalid:

  • expected Jira Issue OCPBUGS-101991 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Remediates CVE-2026-33814, a denial-of-service vulnerability in Go's HTTP/2 implementation (golang.org/x/net) where a malformed SETTINGS_MAX_FRAME_SIZE frame can be used to crash or hang a server.

Changes

  • Added a replace directive in go.mod pointing golang.org/x/net to the patched fork github.com/openshift-sustaining/net@v0.50.0-sec.4.
  • Bumped golang.org/x/net from v0.34.0 → v0.49.0 (via the replace) along with transitively affected golang.org/x/sys, golang.org/x/term, and golang.org/x/text to satisfy go mod tidy.
  • Updated go.sum accordingly.

Testing

  • make build-backend — builds successfully with go 1.24.0.
  • make test-backend — all tests in ./pkg/... pass.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@jgbernalp

Copy link
Copy Markdown
Contributor

@tonyxrmdavidson not sure this is the right approach to fix this, I think it will be better to upgrade the go version in go.mod to 1.26.6 which patches a series of other CVEs. For this, we can check with the ART team, which productizes this plugin, to update to an appropriate go base image for the version mentioned before. Also upgrade to golang.org/x/net v0.56.0 rather than adding a replace directive that will be harder to maintain. WDYT?

@germanparente

Copy link
Copy Markdown
Contributor

@jgbernalp in sustaining we fix the golang cves in all golang versions. So as not to have to bump golang. In this case 4.22 is built by default by ART with 1.25 and we try to keep this fixed.

@jgbernalp

Copy link
Copy Markdown
Contributor

/lgtm

@jgbernalp

Copy link
Copy Markdown
Contributor

/test ?

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Sep 15, 2026
@openshift-ci

openshift-ci Bot commented Sep 15, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jgbernalp, tonyxrmdavidson

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 15, 2026
@jgbernalp

Copy link
Copy Markdown
Contributor

/test e2e-monitoring

@jgbernalp

Copy link
Copy Markdown
Contributor

/label qe-approved

@openshift-ci openshift-ci Bot added the qe-approved Signifies that QE has signed off on this PR label Sep 16, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@tonyxrmdavidson: This pull request references Jira Issue OCPBUGS-101991, which is invalid:

  • expected Jira Issue OCPBUGS-101991 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Remediates CVE-2026-33814, a denial-of-service vulnerability in Go's HTTP/2 implementation (golang.org/x/net) where a malformed SETTINGS_MAX_FRAME_SIZE frame can be used to crash or hang a server.

Changes

  • Added a replace directive in go.mod pointing golang.org/x/net to the patched fork github.com/openshift-sustaining/net@v0.50.0-sec.4.
  • Bumped golang.org/x/net from v0.34.0 → v0.49.0 (via the replace) along with transitively affected golang.org/x/sys, golang.org/x/term, and golang.org/x/text to satisfy go mod tidy.
  • Updated go.sum accordingly.

Testing

  • make build-backend — builds successfully with go 1.24.0.
  • make test-backend — all tests in ./pkg/... pass.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@tonyxrmdavidson

Copy link
Copy Markdown
Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 16, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@tonyxrmdavidson: This pull request references Jira Issue OCPBUGS-101991, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-104374 is in the state Closed (Done), which is one of the valid states (MODIFIED, ON_QA, VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-104374 targets the "5.0.0" version, which is one of the valid target versions: 5.0.0
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@redhat.com), skipping review request.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@tonyxrmdavidson

Copy link
Copy Markdown
Author

/test e2e-monitoring

@openshift-merge-bot
openshift-merge-bot Bot merged commit 676717b into openshift:release-4.22 Sep 16, 2026
9 of 10 checks passed
@openshift-ci-robot

Copy link
Copy Markdown

@tonyxrmdavidson: Jira Issue OCPBUGS-101991: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-101991 has been moved to the MODIFIED state.

Details

In response to this:

Remediates CVE-2026-33814, a denial-of-service vulnerability in Go's HTTP/2 implementation (golang.org/x/net) where a malformed SETTINGS_MAX_FRAME_SIZE frame can be used to crash or hang a server.

Changes

  • Added a replace directive in go.mod pointing golang.org/x/net to the patched fork github.com/openshift-sustaining/net@v0.50.0-sec.4.
  • Bumped golang.org/x/net from v0.34.0 → v0.49.0 (via the replace) along with transitively affected golang.org/x/sys, golang.org/x/term, and golang.org/x/text to satisfy go mod tidy.
  • Updated go.sum accordingly.

Testing

  • make build-backend — builds successfully with go 1.24.0.
  • make test-backend — all tests in ./pkg/... pass.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-merge-robot

Copy link
Copy Markdown
Contributor

Fix included in release 4.22.0-0.nightly-2026-09-16-175651

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants